Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1416

reference
700-tree-1
name
1416
tree-preservation-order

undefined

700-tpo-1
uprn
address-text
point
POINT (-1.010466 50.881199)
geometry
MULTIPOLYGON (((-1.010424 50.881194,-1.010426 50.881202,-1.010432 50.881210,-1.010441 50.881216,-1.010453 50.881220,-1.010466 50.881221,-1.010479 50.881220,-1.010501 50.881211,-1.010507 50.881203,-1.010509 50.881195,-1.010507 50.881186,-1.010501 50.881179,-1.010492 50.881173,-1.010480 50.881169,-1.010467 50.881167,-1.010442 50.881172,-1.010432 50.881178,-1.010426 50.881186,-1.010424 50.881194)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL